Received: from relay4.UU.NET (relay4.UU.NET [192.48.96.14]) by keeper.albany.net (8.7.1/8.7.1) with ESMTP id FAA08828 for <dwarner@albany.net>; Fri, 15 Dec 1995 05:57:30 -0500 (EST)
Received: from garcia.com by relay4.UU.NET with SMTP
id QQzufb24333; Fri, 15 Dec 1995 05:54:38 -0500 (EST)
Received: from (localhost) by garcia.com (5.x/SMI-SVR4)
id AA16565; Fri, 15 Dec 1995 05:54:58 -0500
Date: Fri, 15 Dec 1995 05:54:58 -0500
Errors-To: dwarner@albany.net
Message-Id: <199512151034.CAA16268@cats.ucsc.edu>
Errors-To: dwarner@albany.net
Reply-To: lightwave@garcia.com
Originator: lightwave@garcia.com
Sender: lightwave@garcia.com
Precedence: bulk
From: Adam Ives Chrystie <adamchry@cats.ucsc.edu>
To: Multiple recipients of list <lightwave@garcia.com>
Subject: Re: Another important tip for morphing projects
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO
X-Status:
At 01:15 AM 12/15/95 -0500, you wrote:
>Adamchry@cats.ucsc.edu said:
> Hate to disagree with you, but the position (in Layout space) of morph
>target objects has no bearing on the morphing process. It does not matter
>if the morph target is aligned with the source object -- it could be 100 km
>away down the -Z axis and flipped upside-down and sized inside-out -- it
>makes no difference.
>
No problem..it's okay to disagree..that way we all learn newer , more
effiecient methods and ..heh i guess in my case we learn that we do not have
to be so anal about parenting..but i coulda sworn i was getting errors due
to not parenting the targets after changing the position and rotation of the
first object in a morph chain..i'll run some more testssss later...jusat got
